An agent will write the Lambda, the template and the tests while you read this slide. The cost has moved somewhere else: deciding what to build, agreeing on the seams between our systems, and being able to prove afterwards what was deployed and by whom.
Which is exactly why coming together matters more, not less.
main.Eighteen months of discovery, collapsed into eleven words — and every assumption that used to surface in those eighteen months is now made silently, by the model, in a fraction of a second.
We cannot review every build at agent speed. So we stop reviewing outputs one by one and start encoding design intent where the agent will read it — then let it read the instructions and build following the instructions.
Constraints live in the repo, in prose the agent loads on every session — not in a wiki page nobody opens and no model ever sees.
Governed building blocks a builder composes. The safe choice is also the fastest one available, so nobody has to be talked into it.
Tags, stack naming, registry mirroring, tools/check. If it isn't
enforced by a gate, it is a preference, not an architecture.
Govern every AI app we ship. Review each chatbot, each RAG pipeline, each assistant, one at a time.
The surface grows faster than the review capacity. Policy arrives after the deploy. You are permanently behind.
Govern the agent that does the building. One place where design intent, permissions and guardrails are applied.
Every application it produces inherits them — tagged, IaC, PR-only, auditable — without asking the builder to care.
There is one builder agent and many applications. Governing the narrow end of the funnel is the only version of this that scales — and it's the version where the builder never needs an AWS account, a console login, or a security review to move.
AI orchestrates the development process with planning, task decomposition, architectural suggestions — not just the typing.
Developers retain the ultimate responsibility for validation, decision‑making and oversight.
A sprint is a batching strategy for expensive change. You batch two weeks of work because re-planning costs more than being slightly wrong for a fortnight.
When change is nearly free, batching is pure latency. The ceremony that protected you becomes the thing slowing you down.
Credentials pasted into a Colab cell, a personal account, an unmanaged subscription. No rotation, no owner, no inventory.
Nothing tagged, nothing in IaC. Nobody can answer what is running, who owns it, or what data it can reach.
Spend appears on a card statement. Exposure appears in an incident. Both after the fact.
This isn't recklessness — it's people getting unblocked because we never offered them a fast, safe road. The answer to shadow IT has never been a stricter policy. It's a better default.
A blueprint layer: reusable, governed building blocks that campus builders compose into working applications — knowledge bases, chat frontends, retrieval, identity.
Tagging, secrets handling, least‑privilege roles, inventory and cost attribution arrive inside the blueprint — not as a checklist a builder has to pass.
Builders describe what they want in Claude Code. The pipeline deploys it into an account the platform team controls. PR‑only write access — no console, no keys.
main — starts within secondspipeline/pipeline.ymlmain deploys to a shared AWS account.No console step. No post-merge approval. Everyone works in this
one repo for two days, so a red main blocks every other track
— and a hung stack is worse than a failed one.
Branch protection means PR-only, validate must pass, and a team member merges
their own work. That check is the only automated gate between a branch and
a live account — so run tools/check before you push.
docs/decisions/, so the next team inherits reasoning instead of archaeology.Today, out loud — not by working around it in a PR at 4pm tomorrow. The constraints are deliberate, and they are also ours to change while we're all still sitting here.
main.